Vehicle accessory system

ABSTRACT

Vehicle step assist systems and methods are provided. The steps systems are configured for installation (e.g., after market installation) and use with a vehicle. The system can include a stepping member. The system can further include a vehicle interface configured to electronically communicate with an existing communication bus of the vehicle, such as through a connection with an existing electronics port of the vehicle. A controller of the step system can be configured to process information received from the vehicle interface and, based at least partly on the processing of the information, perform certain operations.

CROSS-REFERENCE TO RELATED APPLICATION

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to a stepping assist for motorvehicles. In particular, the disclosure relates to an automatedretractable vehicle running board which is movable between a retractedor storage position and an extended, deployed position in which itfunctions as a step assist into the vehicle.

BACKGROUND OF THE DISCLOSURE

Running boards or similar stepping assists are sometimes added to theside of a motor vehicle, especially to a vehicle with a relatively highground clearance. While some running boards and other stepping assistsare fixed in place, others are movable between retracted and deployedpositions. Some retractable vehicle steps are automated, where a powereddrive system automatically deploys and retracts the running board, suchas when a door on the step-side of the car is opened and closed,respectively. Automated retractable running boards and other stepassists are often installed after-market, typically by skilledtechnicians.

SUMMARY

An automated step assist solution is needed that can be installed withreduced complexity and expense. The present disclosure relates to anautomated retractable vehicle step system that can be installed in arelatively straightforward and cost effective manner. According tocertain aspects, the step system can be installed by the purchaser in a“do it yourself” fashion without hiring out the install to a technician.The system according to some embodiments includes one or more componentsof the system that plug into, connect with, or otherwise interface withan existing vehicle connection to obtain door status or otherinformation that is generated by existing vehicle electronics.

For example, step system installation can be performed withoutsignificant disassembly and/or modification of the doors and/or otherparts of the vehicle, e.g., without installation of special in-doorcomponentry, removal of door paneling, etc. Embodiments of the stepsystem interface with and leverage existing vehicle componentry todetect door opening and closing events, or to otherwise identify properconditions for effectuating automated movement of the step. Thus, somestep systems described herein do not include after-market installedcomponentry on or around the door for detecting triggering conditionsused in moving the step.

Additionally, according to certain aspects, installation of the stepsystem desirably does not involve cutting, splicing, or tapping intoexisting vehicle wiring, such as wiring residing in the vehicle doors orin the immediate vicinity of the doors (e.g., on the door frames or doorsills). Rather, the step system in some cases includes a connector thatinterfaces with existing accessible vehicle connectors or ports toobtain information from the vehicle that is usable in identifyingtriggering conditions for automated movement of the step (e.g.,identifying door openings and closings). The system according to someaspects obtains the information via one or more existing communicationbuses of the vehicle, e.g., via a digital interface such as a serialdata link. Some preferred embodiments plug into or otherwise interfacewith an on-board diagnostic (OBD) port, for example. The step systemaccording to additional embodiments can interface with ports of existingvehicle computing systems or subsystems such as a body control module(BCM) or another electronic control unit (ECU).

The automated system can additionally include a pass-through functionand a replica of the existing vehicle port. This can provide readyaccess to the existing vehicle port functionality even while the stepsystem is installed and the original port is occupied.

Moreover, step assemblies according to certain aspects primarily orexclusively include wired connections to the existing vehicle and/oramongst components of the step system. For instance, a controller of thestep system may connect via a wired connection to existing vehicleelectronics to access door opening and closing information or otherinformation sufficient to control step movement. Additionally, incertain embodiments the assembly relies on door opening and closinginformation that is generated by wired vehicle componentry (e.g.,in-door circuitry wired to a mechanical door latch) not incorporatingwireless sensors or other componentry, and desirably may convey thisinformation via wires to a step assist control, such as an electronicstep assist control module.

According to certain aspects, a powered retractable vehicle step assistsystem is configured for use with a vehicle. The step assist system caninclude a stepping member having a stepping surface and movable betweena retracted position and a deployed position with respect to thevehicle. At least one support member may be connectable with respect toan underside of the vehicle and connected to the stepping member. Thesupport member can be configured to at least partially support thestepping member with respect to the vehicle. The system can furtherinclude a motor operably coupled to the support member and capable ofeffectuating movement of the stepping member from the retracted positionto the deployed position. A vehicle interface of the system can beconfigured to connect with an already existing electronics port of thevehicle. The vehicle interface can also be configured to electronicallyreceive data via the existing electronics port, where the data generatedby existing electronics of the vehicle. The system can also include acontroller in electronic communication with the motor. The controllercan be configured, in response to the data received from the alreadyexisting electronics port, to cause the motor to effectuate movement ofthe stepping member between the retracted position and the deployedposition.

In some embodiments, the vehicle interface implements a serial digitalinterface, and the existing electronics port provides the data to thevehicle interface as serial digital data. The existing electronics portcan be an on-board diagnostic (OBD) port, for example. The existingvehicle electronics can include a body control module (BCM).

The vehicle interface can in some implementations include an electricalconnector configured to directly attach to the already existingelectronics port of the vehicle. The electrical connector of the vehicleinterface may be configured to mate with the already existingelectronics port via an interference fit, for instance. The system mayinclude wired connection between the vehicle interface and thecontroller.

In various implementations, the vehicle interface includes a firstconnector configured to connect to the existing electronics port andfurther includes a replica connector. The vehicle interface may beconfigured to forward the data received from the existing electronicsport to the replica connector, for example. The vehicle interface caninclude a cable spanning between the first connector and the replicaconnector. The vehicle interface can include a second replica connector,where the controller is coupled to the vehicle interface via connectionto the second replica connector, for example. In some embodiments, thefirst connector and the replica connector are provided on a commonhousing.

According to certain implementations, the controller commands the motorto effectuate movement of the stepping member between the retractedposition and the deployed position in response to determining that adoor vehicle has opened.

In some embodiments, the data comprises door opened/closed statusinformation originating from door electronics that does not incorporateany wireless sensors to detect door opened/closed status.

According to additional aspects, a method is provided of controllingmovement of a powered, retractable vehicle step supported by anunderside of a vehicle. The method can include, with an electronicconnector attached to an already existing electronics port of thevehicle, electronically receiving data generated by already existingvehicle electronics. The method can further include processing the datausing one or more hardware processors according to a step movementalgorithm. Based at least partly on the processing, the method canfurther include electronically initiating movement of the poweredvehicle step between a retracted position and a deployed position. Insome configurations, the electronic connector is attached to theexisting electronics port via a plug in connection.

According to yet other aspects, a method is provided of controlling anafter-market powered vehicle step system installed on a vehicle. Themethod can include electronically obtaining door status information froma digital communication bus of the vehicle. The method can furtherinclude electronically processing the door status information accordingto an algorithm to determine that movement of a stepping deck of thepowered vehicle step is appropriate. Additionally, the method caninclude commanding a motor of the powered vehicle step which is drivablycoupled to the stepping deck to cause movement of the stepping deckbetween a retracted position and a deployed position.

According to certain embodiments, the step of electronically obtainingcan include obtaining the door status information via a pre-existingconnector of the vehicle. The method can further include transmittingthe door status information to electronic componentry of the step systemvia a wired connection. In some embodiments, the step of electronicallyobtaining includes obtaining the door status information via a plug-inconnection to the digital communication bus.

The door status information can be generated by pre-existing componentryof the vehicle. In some embodiments, the door status information isgenerated in response to user actuation of a handle of a door of thevehicle. Moreover, the door status information can be obtained in someembodiments without reliance on disassembly of any portion of any doorof the vehicle. The door status information can be provided to the stepsystem via an existing electrical connector of the vehicle withoutreliance on modification of existing electrical componentry of thevehicle.

According to other aspects of the disclosure, a powered retractablevehicle step assist system is configured for use with a vehicle. Thestep system can include a stepping member movable between a retractedposition and a deployed position with respect to the vehicle. The systemcan further include a drive unit operably coupled to the support memberand capable of effectuating movement of the stepping member from theretracted position to the deployed position. A vehicle interface can beincluded that is configured to electronically communicate with anelectronics port of the vehicle. The system can further include acontroller configured to process information received from the vehicleinterface and, based at least partly on the processing of theinformation, to cause movement of the stepping member between theretracted position and the deployed position. The information can begenerated by existing vehicle electronics, for example. In someembodiments, the information comprises door status information generatedby a car door module of the vehicle.

According to yet another aspect, a method is provided of installing anautomated vehicle step assist system to a vehicle. The method caninclude electrically connecting control electronics of the step assistsystem to an existing power source of the vehicle. The method canfurther include mounting the control electronics of the step assist onthe vehicle. In addition, the method can include mounting a step of thestep assist system with respect to the vehicle such that a stepping deckof the step is capable of powered movement between retracted anddeployed positions. The method can further include securing a motor ofthe step assist system to the vehicle, where the motor in electricalcommunication with the control electronics and drivably coupled to thestep to provide the powered movement of the stepping deck. The methodcan also include interfacing with an existing communication bus of thevehicle such that electronic information obtained via the existingcommunication bus is communicated to the control electronics of the stepassist system. The step of interfacing can include mating a connector ofthe step assist system with an existing connector of the vehicle. Themethod can further include repositioning the existing connector of thevehicle and fastening a replica port of the step assist system to anaccessible location in the vehicle.

In some embodiments, the replica port is positioned in substantially theoriginal location of the existing connector of the vehicle. In certainimplementations, the interfacing does not involve disassembly of thevehicle. The step of interfacing in some embodiments includesestablishing a wired connection between the existing communication busand the control electronics of the step assist system. The installationcan be performed after market, for example.

According to further embodiments, a method is disclosed of providing apowered vehicle step assist configured for use with a vehicle, themethod can include providing a stepping member having a stepping surfaceand movable between a retracted position and a deployed position withrespect to the vehicle. The method can further include providing atleast one support member connectable with respect to an underside of thevehicle and connected to the stepping member, the support memberconfigured to at least partially support the stepping member withrespect to the vehicle. In addition, the method can include providing amotor operably coupled to the support member and capable of effectuatingmovement of the stepping member from the retracted position to thedeployed position. The method can also include providing a connectorconfigured to mate with an already existing electronics port of thevehicle and to electronically receive data via the electronics port, thedata generated by existing electronics of the vehicle. The method can insome cases also include providing a controller in electroniccommunication with the motor. The controller can be, in response to thedata received from the already existing electronics port, to cause themotor to effectuate movement of the stepping member between theretracted position and the deployed position.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B illustrate an embodiment of a retractable running boardinstalled on a vehicle, in retracted (FIG. 1A) and deployed (FIG. 1B)positions.

FIG. 2A illustrates portions of an automated step system including avehicle interface that cooperates with an existing vehicle port,according to an embodiment.

FIG. 2B depicts portions of an automated step system according toanother embodiment, where the vehicle interface of the step systemincludes two replica vehicle ports.

FIG. 2C illustrates an existing vehicle port connection prior toinstallation of an automated step system.

FIG. 2D illustrates portions of an automated step system according toanother embodiment, after installation, where the vehicle interface ofthe step system is interposed in the existing vehicle port connectionshown in FIG. 2C.

FIG. 2E shows an exemplary connection configuration of an electroniccontrol unit of a vehicle prior to installation of an automated stepsystem.

FIG. 2F shows an embodiment of a vehicle interface of an automated stepsystem, after installation, where the vehicle interface is connected toan existing electronic control unit of the vehicle.

FIG. 2G shows an embodiment of a vehicle interface including an overrideswitch.

FIG. 3 is a block diagram illustrating an exemplary automated stepsystem in the context of a host vehicle system.

FIG. 4 is a perspective view of one example of a retractable vehiclestep.

FIG. 5 is a flowchart depicting an exemplary method of installing anautomated vehicle step of embodiments described herein.

FIG. 6 is a flowchart depicting an exemplary method of operation for anautomated vehicle step of embodiments provided herein.

DETAILED DESCRIPTION

For purposes of summarizing the disclosure, certain aspects, advantagesand novel features of the disclosures have been described herein. It isto be understood that not necessarily all such advantages can beachieved in accordance with any particular embodiment of the disclosuresdisclosed herein. Thus, the disclosures disclosed herein can be embodiedor carried out in a manner that achieves or optimizes one advantage orgroup of advantages as taught herein without necessarily achieving otheradvantages as can be taught or suggested herein.

The terms “existing”, “pre-existing”, “pre-installed”, “at manufacture”,and other similar terms, are used herein to refer to certain vehiclecomponentry. Such terms can refer to vehicle componentry installed whenthe vehicle was originally assembled, as opposed to componentryinstalled after-market. These terms can additionally encompassreplacement parts, such as installed replacement parts manufactured bythe original equipment manufacturer (OEM).

FIGS. 1A-1B illustrate one illustrative example of a retractablerunning-board step assist 100 attached to an underside of a vehicle 110,in retracted (FIG. 1A) and deployed (FIG. 1B) positions. The step assist100 can be mounted to any type of motor vehicle suitable foraccommodating a step assist, including light duty and heavy duty trucks,sport utility vehicles, vans, sedans, hatchbacks, etc.

The illustrated step assist 100 includes a stepping member or deck 120having an upper step surface 122. It is readily seen that the steppingdeck 120 provides a convenient step assist for a person desiring toenter the vehicle 110 through either of the front and rear vehicledoors.

The exemplary step assist 100 further includes respective supportassemblies 130 each of which terminate at a first end attached towards arespective end of the stepping deck 120 and at a second end attached toor otherwise supported by the underside of the vehicle 110. Although avariety of configurations are possible, each support assembly 130 in theillustrated embodiment includes a support bracket 132 attached towardsor at an end of the stepping deck 120 and pivotably coupled to a pair ofsupport arms 134 a, 134 b. The support arms 134 a, 134 b are in turnmounted to the underside of the vehicle 110, via a rigid mount frame(not shown) or other appropriate mechanism.

As shown, the step assist 100 is provided on one side of the vehicle110, underneath the front and rear vehicle doors. One or more additionalstep assists may be provided at other locations such as the other sideof the vehicle 110 or on the rear of the vehicle in conjunction with arear door, hatch, tailgate, etc.

The step assist 100 shown in FIGS. 1A-1B is merely one illustrativeexample. Compatible step assists 100 can vary. For instance, theillustrated step assist 100 spans the length of both front and reardoors and can therefore assist passengers with entering and exiting bothfront and rear doors. In other cases a shorter stepping deck 120 isprovided, which may span the length of only a single door or a portionthereof. Another more detailed example of a step assist that can beincorporated into any of the step systems described herein is shown inFIG. 4, described below. Further examples of compatible step assists aredescribed throughout the disclosure, as well as in U.S. Pat. No.8,157,277, titled “Retractable Vehicle Step”, issued on Apr. 17, 2012,and U.S. Pat. No. 7,367,574, titled “Drive Systems for RetractableVehicle Step”, issued on May 6, 2008, the entire disclosures of whichare incorporated by reference herein.

The step assist 100 is configured for automated, powered retraction anddeployment. For instance, the step assist 100 can form part of anautomated step system including a drive unit that includes a motordrivably coupled to the step assist 100, e.g., via one or more of thesupport arms 134 a, 134 b, for powered retraction and deployment of thestepping deck 120.

The automated step system can further include a controller (not shown)that instructs the motor to effectuate movement of the step assist 100.The controller can be in communication with existing vehicle systems viaa vehicle interface of the step system. FIG. 2A illustrates a controller210 and vehicle interface 220 of an embodiment of an automated stepsystem configured for use with a vehicle 230. While only the controller210 and vehicle interface 220 of the step system are shown forillustrative purposes, it is to be understood that embodiments of thestep system, including the illustrated embodiment, include additionalcomponentry such as a drive assembly, stepping deck, etc., such as isshown and described herein, e.g., with respect to FIGS. 3 and 4.

As indicated, the illustrated controller 210 includes a housing 212having at least one connector 214 configured to mate with at least onecorresponding connector 215, thereby connecting the controller 210 withwiring 216, 217, 218 of the step system. For instance, the illustratedcontroller 210 is in communication with a motor and/or other componentsof a drive unit of the step system via the wiring 216, receives powervia the wiring 217, and is in communication with the vehicle interface220 via the wiring 218. In some configurations, the wiring 217 isconnected to an existing vehicle battery, thereby delivering power tothe automated vehicle step system without necessitating a separate powersupply. In alternative embodiments, the step system connects to thevehicle battery indirectly, such as through a power socket located inthe vehicle interior, or includes a separate power supply.

The controller 210 includes control electronics (not shown) which, inthe illustrated embodiment reside within the housing 212. For example,the control electronics can include one or more hardware processorscomprising digital logic circuitry (e.g., one or more microcontrollersexecuting software and/or firmware), computer memory, and otherappropriate circuitry. The control electronics is generally configuredto process data received from the vehicle interface 220 and issuecommands to the drive assembly of the step system to control poweredmovement of the step assist.

The vehicle interface 220 includes a connector module 222 having a port224 that is configured for mechanical and electrical cooperation with anexisting port 240 of the vehicle 230. In the illustrated embodiment, theport 224 implements a friction fit with the existing vehicle port 240,although a variety of other mating mechanisms are possible instead of,or in combination with a friction fit, including latch, interference, orsnap-fit mechanisms, mechanisms including fastening screws, and thelike. While the illustrated connector module 222 attaches directly tothe existing vehicle port 240, in some alternative configurations anadaptor or other component (e.g., an after-market adaptor) may beattached to and interposed between the existing vehicle port 240 and thevehicle interface 220.

The existing vehicle port 240 is in communication with one or moreexisting electronic systems of the vehicle 230, and provides vehiclestatus information. The vehicle interface 220 of the step systemreceives this information via the electrical connection between its port224 and the existing vehicle port 240. As is described further, thestatus information of certain embodiments (including the illustratedembodiment) includes, without limitation, information relating to thestatus of one or more doors of the vehicle 230, usable in identifyingconditions for deploying/retracting the stepping member.

The step system in some embodiments such as those of FIGS. 2A-2F obtainsinformation over an existing electrical communication bus of the vehiclethat is usable to determine when to move the step. For instance, thestep system obtains information over a digital communications bus suchas a serial communications link. Such communications buses can beprovided over the existing vehicle port 240, such as a serial digitalinterface provided on an OBD-II port.

Installation of embodiments of the step system such as those of FIGS.2A-2F desirably rely on accessible vehicle communication ports withoutcutting, splicing, or tapping into existing vehicle wiring, such aswiring residing in or around the vehicle doors, or elsewhere in thevehicle. Rather, such step systems leverage entirely or substantiallyentirely existing componentry (e.g., manufacturer installed or OEMcomponentry) to obtain door opening or closing information via anexisting communication bus of the vehicle.

In addition, the step systems of certain embodiments including the onesdepicted in FIGS. 2A-2F incorporate wired as opposed to wirelessconnections, e.g., between the drive assembly and the controller 210 viathe wiring 216, between the vehicle interface 220 and the controller 210via the wiring 218, and/or between the vehicle interface 220 and theexisting vehicle port 240. This can significantly simplify the design,increasing operational robustness and reducing costs. For instance,wireless systems can be costly and in some cases are susceptible tointerfere with or be subject to interference from other wireless signalsin the proximity of the vehicle. In some alternative embodiments, one ormore of the above-listed connections incorporate a wireless interface.

Moreover, step systems such as those depicted in FIGS. 2A-2F obtain dooropening and closing information (or for otherwise determining when tomove the step) via an accessible communication bus of the vehicle whilerelying solely or primarily on existing, pre-installed componentry toprovide the information over the bus. For instance, installation of theembodiments of FIGS. 2A-2F do not involve installation of after-marketcomponentry in the vehicle doors, in the immediate vicinity thereof(e.g., the door sills and door frame), or otherwise. Instead, theexisting vehicle port 240 provides such information. This can beespecially beneficial in contrast to solutions that rely on after-marketinstallation of sensing componentry on the door or in the vicinity ofthe door to detect door opening and closing events. This is at leastpartly because such systems can include costly and complex componentrythat can become dislodged or damaged due to the forces associated withrepeated door opening and closing, particularly over long periods oftime. In contrast, manufacturer installed and OEM parts (e.g., existingdoor latches and associated electronics) typically undergo extensivequality control measures under highly regulated conditions, and are alsointegrated into the original vehicle design. Such components aretherefore more likely to withstand such wear and tear over time.Nonetheless, in some alternative embodiments, the step system canincorporate some amount of after-market componentry for detecting dooropening/closing events.

In one embodiment, the vehicle interface 220 includes processingelectronics (not shown) configured to process the information receivedfrom the existing vehicle port 240. The processing electronics canreside within the housing of the connector module 222 and can includeone or more hardware processors comprising digital logic circuitry(e.g., one or more microcontrollers executing software and/or firmware),memory, and other appropriate circuitry. The processing module canfurther include circuitry configured to condition the received signalsfor delivery to the step controller 210 via the wiring. In someembodiments, the processing module converts the information receivedfrom the existing vehicle port 240 into a protocol or format that isunderstandable by the controller 210. In one embodiment, the processingelectronics converts information received from the existing vehicle port240 from a first format (e.g., an OBD-II compliant serial format) into asecond format (e.g., an RS232 serial interface). The processingelectronics can in some cases perform additional data processing. Forinstance, the processing electronics may identify information relevantto operation of the automated step system (e.g., information relating tothe operation and status of the vehicle doors) for delivery to thecontroller 210, while filtering out other data not relevant to stepsystem operation (e.g., certain engine status information or the like).For example, the vehicle interface 220 can process the informationreceived over the vehicle port 240 and provide outputs to the controller210 indicate the state of the drivers and/or passenger side doors. Inyet other configurations, the connector module 222 forwards the receivedinformation to the controller 210 without manipulating the receivedinformation. In such cases, the control electronics of the controller210 may implement some or all of the functionality described withrespect to the processing electronics of the vehicle interface 220.

The illustrated example shows the existing vehicle port 240 locatedunder the dashboard 232 above the passenger side foot well of thevehicle 230, although a variety of other locations are possible. Forinstance, depending on the embodiment, the existing vehicle port 240 maybe positioned anywhere on the interior or exterior of the vehicle,including, without limitation, in the glove compartment, on thedashboard, in the engine compartment under the hood, in the trunk, onthe underside of the vehicle 230, or somewhere on or in the centerconsole between the driver and passenger seats. In certain embodiments,the existing vehicle port 240 is positioned at a location such that itis accessible for connection thereto without removing or disassemblyexisting parts of the vehicle 230.

The existing vehicle port 240 can generally comprise any pre-existing(e.g., factory installed) port that provides access to the existingelectronics systems of the vehicle 230. For instance, the existingvehicle port 240 in the illustrated and other embodiments can be anon-board diagnostic (OBD) port. Depending on the embodiment, theexisting vehicle port 240 can be compliant with any appropriate OBDstandard, including without limitation the following: ALDL, OBD-I,OBD-1.5, OBD-II, European On-board Diagnostics (EOBD), EOBD2, JapanOn-board Diagnostics (JOBD), and Australian OBD standards (e.g., ADR79/01 and 79/02). The existing vehicle port 240 can be compliant withthe OBD-II standard mandated by the federal Clean Air Act Amendments of1990, for example. Where the existing port 240 is an OBD-II port, it mayfurther provide data in a manner that is compliant with one or more ofthe serial data protocols defined in the SAE J1850 standards document,such as the SAE J1850 pulse-width modulation (PWM) and SAE J1850 VPW(variable pulse width) protocols. In some cases, the existing vehicleport 240 complies with the SAE J1962 standards document defining thephysical connector for the OBD-II interface, and which specifies the16-pin arrangement set forth in the table provided below.

Pin Signal Description 1 Manufacturer discretion. GM: J2411GMLAN/SWC/Single- Wire CAN. VW/Audi: Switched +12 to tell a scan toolwhether the ignition is on. 2 Bus positive Line of SAE-J1850 PWM andSAE-1850 VPW 3 Ford DCL(+) Argentina, Brazil (pre OBD-II) 1997-2000,USA, Europe, etc. Chrysler CCD Bus(+) 4 Chassis ground 5 Signal ground 6CAN high (ISO 15765-4 and SAE- J2284) 7 K line of ISO 9141-2 and ISO14230-4 8 Manufacturer discretion. Many BMWs: A second K-Line for nonOBD-II (Body/Chassis/Infotainment) systems. 9 Manufacturer discretion.GM: 8192 baud ALDL where fitted. 10 Bus negative Line of SAE-J1850 PWMonly (not SAE-1850 VPW) 11 Ford DCL(−) Argentina, Brazil (pre OBD-II)1997-2000, USA, Europe, etc. Chrysler CCD Bus(−) 12 — 13 Manufacturerdiscretion Ford: FEPS - Programming PCM voltage 14 CAN low (ISO 15765-4and SAE- J2284) 15 L line of ISO 9141-2 and ISO 14230-4 16 Batteryvoltage

In various embodiments, the vehicle interface 220 can be configured tocooperate with a variety of other types of existing vehicle ports 240other than OBD ports, such as a port of a body control module (BCM) orother electronic control unit (ECU) of the vehicle 230. Further detailsregarding compatible existing vehicle ports and the types of informationreceived from the existing vehicle port are provided herein, withrespect to FIG. 3, for example.

Additional Vehicle Interface Configurations; Port Replication; OverrideFunction

In some cases, the vehicle interface 220 is configured to allow normaluse of the existing vehicle port 240 functionality while the vehicleinterface 220 is plugged into the existing vehicle port 240. Forexample, FIG. 2B shows an embodiment of a vehicle interface 220 thatincludes a three-port connector apparatus 226 including a hub connector227 for interfacing with the existing vehicle port 240, a first replicavehicle port 228 for interfacing with the connector module 222, and asecond replica vehicle port 229. The first and second replica vehicleports 228, 229 can include the same or substantially the same mechanicaland electrical connection interface as the existing vehicle port 240.

Moreover, the connector apparatus 226 provides a pass-through functionby forwarding or replicating the output of the existing vehicle port 240at outputs of the first and second replica vehicle ports 228, 229. Inthis manner, the first replica vehicle port 228 can interface with theconnector module 222 for use in operating the automated step system,while the second replica vehicle port 229 provides access to theexisting vehicle port 240 functionality for its customary purpose. Forinstance, where the existing vehicle port 240 is an OBD-II port,automotive technicians can connect OBD-II compliant diagnostic scannersto the second replica vehicle port 229 for diagnostic purposes while theautomated step system remains completely intact and installed. In oneconfiguration, the existing vehicle port 240 is physically unfastenedfrom its normal location (while remaining electrically connected asnormal), and the second replica vehicle port 229 is fastened in place ofthe existing vehicle port 240 so that installation of vehicle interface220 is substantially transparent to technicians and others desiring touse the existing vehicle port 240 while the step system is installed.

FIG. 2D shows an embodiment of a vehicle interface 220 providing only asingle replica port 229 which provides standard access to the existingvehicle port 240. Unlike the embodiment of FIG. 2B, the connector module222 itself includes the replica port 229, and an intermediate componentsuch as the connection apparatus 226 of FIG. 2B is not used to provideport replication. The replica vehicle port 229 is provided on thehousing of the connector module 222 in FIG. 2D, providing a compactdesign. In another embodiment, the replica vehicle port 229 can beprovided on a separate connector that attaches to the housing of theconnector module 222 via cabling.

As depicted in FIG. 2C (prior to step system installation) and FIG. 2D(post-step system installation), the vehicle interface 220 in some casescan be interposed between the existing vehicle port 240 and anotherconnector 242. The connector 242 is configured to interface with theexisting vehicle port 240, and in some embodiments is a connector of adevice that is external to the vehicle, such as an OBD diagnosticscanner where the port is an OBD port. In other cases, the connector 242comprises an existing vehicle connector that normally occupies theexisting vehicle port 240. FIGS. 2E and 2F illustrate one suchconfiguration, where the existing vehicle port 240 is a port of acomputer system or subsystem 250 of the vehicle 230. The computer system250 can be an electronic control module (ECU) of the vehicle 230, forexample, which is generally an embedded electronics system that controlsand/or monitors one or more of the electrical subsystems in the vehicle230.

Referring to FIG. 2E, the connector 242 terminates cabling 244, andordinarily occupies the existing vehicle port 240 of the computer system250 during normal vehicle operation. The connector 242 and cabling 244carry information between the computer system 250 and appropriatevehicle componentry. For instance, the computer system 250 of someembodiments including the illustrated embodiment can be a body controlmodule (BCM) configured to control door locks, power windows, interiorlighting, and the like. The cabling 244 carries information between theBCM and various subsystems of the vehicle which are regulated ormonitored by the BCM, such as the doors (e.g., door locks, door handles,door open/closed sensors), windows, interior lighting, power seats, airconditioning, anti-theft system, gauges, and other appropriate vehiclecomponents. Other types of ECU's and other computing systems that can beused in conjunction with the step assist are described herein, e.g.,with respect to FIG. 3.

As represented in FIG. 2F, following installation of the automated stepsystem the vehicle interface 220 is interposed between the vehiclecomputer system 250 and the connector 242. The pass-through function ofthe vehicle interface 220 enables normal communication between thecomputer system 250 and the connector 242, thereby making installationof the step system substantially transparent with respect to operationof the computer system 250.

FIG. 2G shows an embodiment of a vehicle interface 220 including anoverride switch 251 that provides such functionality. While automateddeployment based on door opening and closing (or other appropriateinputs) is useful in many situations, it can be desirable to allow thevehicle operator to manually control powered step retraction anddeployment in certain cases. For instance, the stepping deck oftenbecomes soiled given its proximity to the ground, wheels, and exposureto foot traffic. Thus, it can be desirable to wash the stepping deck.However, it is generally impractical to wash a vehicle having an opendoor, and it can therefore be desirable to allow for deployment whilethe doors are closed. As another example, sometimes obstacles (e.g.,rocks in off-road environments) are positioned in the step deploymentpath, such that deployment could cause cosmetic or other damage to thestep. Users may nonetheless want to open the door to exit the vehicle.In this and other scenarios it can therefore be useful to provide anoverride mode that keeps the step in a retracted position even when thedoor is opened.

While the term “manual” is used with respect to the override mode, thisrefers to the fact that the user is directly controlling step movementusing the switch 251 rather than relying on an automated algorithm. Itdoes not imply that the user physically manipulates the step. Rather,the override mode still preferably involves powered movement of the stepin response to actuation of the switch 251.

A variety of different types of switches are possible which cangenerally include a combination of appropriate mechanical and electricalcomponents which function together to provide the desired overridefunctionality. In one illustrative example, the override switch 251 is a3-state toggle switch movable between a first, center position in whichthe step moves according to the normal automated scheme (e.g., inresponse to detected door openings and closings). Toggling the switch251 in a first direction away from the center position to a secondposition initiates a manual retract mode which overrides the normalautomated step movement scheme. If the step is deployed at the time theswitch 251 is moved to the second position, the step moves to theretracted position, e.g., regardless of the state of the door or ofother control inputs. If the step was already in a retracted position,toggling the switch 251 to the second position will not move the step.However, in some embodiments the step will remain retracted even if adoor is subsequently opened, so long as the switch 251 remains in thesecond position. Toggling the step in a second direction away from thecenter position to a third position initiates a manual deploy mode whichoverrides the normal automated step movement scheme. If the step isretracted at the time the user moves the switch 251 to the thirdposition, the step deploys, e.g., regardless of the state of the door orof other control inputs. If the step was already deployed, toggling theswitch 251 to the third position will not move the step. However, insome embodiments the step will remain deployed even if a door issubsequently closed, so long as the switch 251 remains in the thirdposition. In some embodiments, the switch 251 does not remain in thesecond or third positions, but instead returns to the center positionafter the user lets go of the switch 251. In such cases, the step willretract or deploy as appropriate when the switch 251 is moved to thesecond or third positions, but normal automated deployment will resumeonce the switch returns to the center position, and subsequent dooropenings and closings will cause retraction/deployment accordingly. Avariety of other types of switches 251 or other user input devices canbe provided to engage the override function, including one or morebuttons, a touch screen, remote control, or the like. In an alternativeembodiment, initiation of an override mode allows the user to physicallyretract and deploy the step as desired, instead of relying on poweredmovement.

Moreover, the override switch 251 can be positioned in a location thatis accessible to the vehicle operator, e.g., when seated in the driver'sseat. For example, referring to FIGS. 2B and 2G, inclusion of theoverride switch 251 on the connector module 222 of the vehicle interface220 can be convenient in cases where the existing vehicle port 240 ispositioned in a manner similar to FIG. 2B. For instance, a user coulddesirably reach down while seated to actuate the switch 251. While theillustrated switch 251 is included on the connector module 222, theswitch 251 can be positioned on another component of the step system,such as the stepping deck, linkage, or drive unit. Or the switch 251 canbe provided with a separate housing and be connected to the controller210 via a wired or wireless connection, facilitating positioning of theswitch 251 at any convenient location within the interior or on theexterior of the vehicle.

Exemplary Installed Automated Step System

FIG. 3 is a schematic diagram depicting an exemplary automated stepsystem 300 installed in an existing vehicle 302. The automated stepsystem 300 may be installed after market, for example, and can include avehicle interface 304, a step controller 306, a drive unit 308, linkage309, and a stepping deck 310.

The existing vehicle 302 can include one or more door subsystems 312corresponding to one or more doors of the vehicle 302 (e.g., 2, 4 ormore doors depending on the vehicle), a plurality of other vehiclesubsystems 314, one or more vehicle computing systems 316 having atleast one existing vehicle port 334, one or more stand-alone existingvehicle ports 318, and a power source 319. As shown, the variouscomponents can be in communication with one another via one or morevehicle communication buses 320. The automated step system 300 of FIG. 3and corresponding components may be the same or similar to any of theautomated step systems and corresponding components described herein,such as any of those described with respect to FIGS. 1A-1B, 2A-2F, and4, for example.

As shown, the components of the vehicle 302 are connected via at leastone communication bus 320. The bus 320 can implement one or a pluralityof appropriate bus types, which can include, without limitation, acontroller area network (CAN) bus (e.g., a CAN 2.0 compliant bus), aDomestic Digital Bus (D2B), a FlexRay bus, and a Local InterconnectNetwork (LIN). Taken together, the bus 320 and the components attachedto the bus 320 may be referred to as a Local Area Network (LAN) orVehicle Area Network (VAN). In one embodiment, vehicle interface 304 isa J1962 compliant OBD port that provides open-collector outputs to thecontroller 306 indicating the state of the driver and passenger sidedoors based on messages received from the vehicle's controller areanetwork (CAN) bus 320.

Each door subsystem 312 can include existing vehicle electronicsconfigured to control operation of the corresponding vehicle door(s).The door subsystem 312 can also be configured to generate and/or processsignals related to operational status of the door, and provide suchinformation to the bus 320. For example, in some embodiments includingthe illustrated embodiment the door subsystem 312 can be an electronicmodule (e.g., a car door module) residing with the corresponding door.The electronic module can include appropriate electrical componentry(e.g., one or more microcontrollers, circuitry, and correspondingsoftware or firmware) for controlling some or all of the car doorfunctions, such as window lift, latching/locking operations, wing mirrormovement, etc. In one embodiment, the door subsystem 312 is an AN2334Complete Car Door Module provided by ST Microelectronics. The doorsubsystem 312 in some embodiments communicates with one or more othercomponents of the vehicle over a LIN bus.

The door subsystem 312 generally operates together with mechanicalcomponents of the door to generate door status information. Forinstance, the doors of the vehicle 302 can generally include amechanical latch operably coupled to interior and exterior door handles.The latch is a spring-activated latch coupled to the handles via a latchrelease cable, for example. When the door is closed and the handles arein their relaxed position, the latch mates with a corresponding catch onthe door frame, securing the car door shut. When the handle is actuatedby the passenger, the latch releases the catch, allowing the car door toopen. The door subsystem 312 can include an electrical trigger switchand other appropriate electronics responsive to an actuation, position,or state of the handle, the latch, or both, or that is otherwiseresponsive to the interaction between the handle and the latch togenerate a signal indicating whether the door is open or closed.Depending on the type of vehicle 302, the door subsystem 312 in somealternative embodiments can include existing, pre-installed sensorcomponentry such as one or more magnets, proximity sensors, or the like.In such cases, one part of the proximity sensor (e.g., a magneticproximity sensor) may be positioned on the door, and the other part maybe positioned on the door frame, such that opening and closing the dooris usable to detect door opening and closing due to the resulting changein proximity of the two parts of the sensor. The door subsystem 312provides a “door ajar” signal to the bus 320 in some embodiments.

The vehicle 302 can include a variety of other existing vehicle systems314, which, like the door subsystem(s) 312, generally include electroniccomponentry associated with different parts of the vehicle 302. Similarto a car door module, the other vehicle systems 314 can includeintegrated electronic modules including collections of components forcontrolling corresponding vehicle subsystems. Or the other vehiclesystems 314 can comprise discrete componentry such as, withoutlimitation, one or more seat occupancy sensors (e.g., pressure sensors),interior lighting control electronics, transmission componentry,ignition componentry, etc. As with the door subsystems 312, some or allof these other vehicle systems 314 may provide information to the bus320 which is ultimately usable by the step system in determining whetherto move the stepping deck 310. For instance, such information isreceived via the bus 320 by an appropriate vehicle computing system 316or vehicle port 318, and then made available to the automated stepsystem 300 via the vehicle interface 304.

The vehicle computing systems 316 can generally comprise any vehiclerelated computer system or subsystem. In particular, the vehiclecomputer systems 316 can include any type of vehicle ECU or other modulethat provides information sufficient to determine when it is appropriateto move or otherwise control the stepping deck 310. Examples include acentral control module (CCM), general or generic electronic module(GEM), door control unit (DCU), engine control unit (ECU), seat controlunit (SCU), and transmission control unit (TCU), speed control unit(SPU) without limitation.

The vehicle computing system 316 includes at least one first port 334which is normally occupied during vehicle operation by a connectorproviding a connection to the bus 320. The vehicle computing system 316can also include at least one second port 336 that is normallyunoccupied and provides electronic access to the computing system 316for diagnostic or other purposes without disconnection from the bus 320.

The vehicle port(s) 318 can include any of the OBD ports describedherein or some other type of appropriate existing port of the vehicle302. For example, the vehicle port(s) 318 can include stand-alone portsthat are not integrated with an ECU or other vehicle computing system316. In some cases, the vehicle port 318 receives status informationfrom a plurality of components including one or more of the vehiclecomputing system(s) 316, door subsystem(s) 312, and other vehiclesystems 314, and presents the information on its output. For instance,where the port 318 is an OBD-II port, it can receive diagnostic and/orother information from some or all of the vehicle ECUs and/or otherelectronics connected to the bus 320.

As shown, the vehicle interface 304 of the step system 300 includes aport 324 adapted to connect with existing vehicle ports such as thefirst port(s) 334 of the vehicle computing system 316 (e.g., similar tothe embodiment shown in FIG. 2F), the second port(s) 336 of the vehiclecomputing system 316, or to the existing port(s) 318 (e.g., similar tothe embodiments shown in FIGS. 2A and 2B). As discussed previously, thevehicle interface 304 can further include processing electronics 326 forprocessing data received from the vehicle 302 via the port 324 (e.g.,door status information) and/or one or more replica ports 328 providingfunctional access to the existing vehicle ports that occupied by thevehicle interface 304.

Operation of the vehicle interface 304 according to an illustrativeembodiment will now be described, as may be executed by a software orfirmware algorithm executing on one or more microcontrollers or otherhardware processors of the vehicle interface 304, for example. Thevehicle interface 304 first enters an initialization or configurationmode when the vehicle interface is plugged into or otherwise attached tothe vehicle port 318 (or other interface on the vehicle 302). Thevehicle interface 304 may also enter the configuration mode when thevehicle battery or other power source 319 is connected or reconnected tothe step system 300. In the initialization mode, the vehicle interfaceruns an initialization or boot procedure and then can wait apredetermined period of time while listening to the vehicle bus 320,which is a can bus in the example embodiment. If no configurationmessages are received, the vehicle interface 304 enters a run mode. Theoutputs of the vehicle interface 304 (e.g., open collector outputs) tothe controller module 306 are inactive in the initialization mode, forexample. In one embodiment, the vehicle interface comprises a separateoutput for each step, e.g., one output for each of a driver andpassenger side running board.

Upon entry to run mode, the state of doors as represented on the outputsof the vehicle interface 304 is “closed”. Messages on the CAN or othervehicle bus 320 are checked against one or more internal filters todetect state changes of any of the doors. If any of the doors are openwhen the vehicle interface 304 enters the run mode, the door should beclosed in the example embodiment in order for the vehicle interface 304to initialize properly and know its state.

For a two door vehicle, the logic of the vehicle interface 304 in theexample embodiment is as follows: if the driver door is open, theappropriate output of the vehicle interface 304 to the controller 306 isactive; if the passenger door is open, the appropriate output of thevehicle interface to the controller 306 is similarly active. For a fourdoor vehicle according to the example, if either of the front or reardoor is open on the driver or passenger side, the corresponding outputof the vehicle interface 304 is active. Conversely, if both the frontand rear door is closed on the driver or passenger side, thecorresponding output is inactive.

If an output is activated during run mode, it can be checked forover-current or other error conditions, and if such conditions exists,the output may be deactivated immediately or soon thereafter, e.g.,until the next CAN message on the bus indicates that the output shouldbe activated. This procedure can repeats each time the output activated.When there are no further CAN or other bus messages to process, e.g.,after a threshold period of time expires (e.g., between 30-60 secondsafter a key-off or other detected action), the vehicle interface 304 canenter a relatively lower power idle mode.

In the idle mode, the vehicle interface 304 can place some most of theprocessor resources of the vehicle interface 304 in a standby or otherlow power condition. In the example embodiment, the only three resourcesthat remain active are a CAN interface module of the vehicle interface304, a timer module, and a power supply monitor, or at least these threemodules can remain active. If the CAN module receives a vehicle messagein idle mode, the vehicle interface can return to run mode to processit. Otherwise, the vehicle interface 304 can check the vehicle batteryvoltage periodically (e.g., every 1 or more seconds). If the voltagedrops below a threshold amount (e.g., less than two thirds of the normalpower supply voltage such as 8 volts for a 12 volt battery), and/or noCAN message is received for a threshold period of time (e.g., at least 5minutes), the vehicle interface 304 can enter a sleep mode.

In sleep mode, the vehicle interface places the CAN interface (e.g., aCAN transceiver) in a special sleep mode and then completely orsubstantially completely shuts down the microcontroller(s) of thevehicle interface 304. When awakened, the microcontrollers can enter arun mode.

The step controller 306 is communication with the vehicle interface 304and can generally include hardware (e.g., one or more microcontrollers,memory, and circuitry) and/or software configured to control operationof the automated step system 300. For instance, the controller 306processes control inputs received from the vehicle interface 304 andsends appropriate control signals to the drive unit 308. In someembodiments one or more processors of the controller 306 execute analgorithm for determining when to move the stepping deck 310, based onthe received control inputs. The algorithm can in some cases be updatedafter purchase, which can be helpful to maintain compatibility of thestep system 300 with a wide variety of vehicles such as newly releasedvehicles which may implement updated communication protocols (e.g.,updated OBD protocols) or other technological developments.

The automated step system 300 can include an interpretation module whichmay include software, firmware, and/or associated electronics (e.g., oneor more microcontrollers or other processors) configured interpret orotherwise process the information received from the vehicle into aformat that is usable by the step system for determining when to movethe step. For instance, the interpretation module may processes serialdata received via an OBD port, a port of a BCM, or some other existingelectronics port 240 in a manner that makes the information usable bythe step system. Depending on the embodiment, the interpretation modulemay be implemented in the controller 306, the vehicle interface 304, acombination thereof, or in some other component of the step system 300.In one embodiment, interpretation module is provided by Cubic Systems,Inc., of Ann Arbor Mich.

It is to be understood from the disclosure that a variety of differenttypes of information can be used by the step system 300 to control stepmovement. Moreover, the information can originate from a variety ofdifferent existing vehicle sources and be delivered to the vehicleinterface 304 of the step system 300 via different intermediarycomponents (e.g., one or more ECU's and/or an OBD port). The followingtable provides a non-exhaustive list of some embodiments. A furtherdescription of various types of components and associated informationand decisioning schemes that can be used is provided with respect toFIG. 6.

The drive unit 308 can include a motor 330 drivingly connected to acoupling 332, which can include a torque limiter and/or appropriate gearsystem, for example. The motor 330 responds to the control signalsreceived from the step controller 306 to act through the coupling 332 tocause the linkage 309 to move, thereby effectuating movement of thestepping deck 310 to the extended or retracted position, as desired. Thelinkage 309 can include support arms and/or other appropriatecomponentry connecting the stepping deck 310 to the drive unit 308. Adetailed example of portions one compatible step assist including anexemplary drive unit, linkage, and stepping deck is provided below withrespect to FIG. 4.

As shown, power can be provided to the step system 300 from a vehiclebattery or other existing power source 319. For instance, the controller306 may connect to the vehicle power source 319 and deliver power to thedrive unit 308, vehicle interface 304, and other appropriate componentsof the step system 300, similar to the manner described with respect tothe embodiments of FIG. 2.

Depending on the embodiment, the physical arrangement of the step system300 components can vary. For instance, while the step controller 306 canbe housed in a separate housing, in some other implementations it isincluded in a common housing with the drive unit 308 or the vehicleinterface 304, or portions thereof.

Exemplary Step Assist

FIG. 4 depicts another embodiment of a retractable vehicle step system400. The terms “forward,” “front” and “outboard” are usedinterchangeably herein, as are the terms “rearward,” “rear” and“inboard,” when describing components of the step structures disclosedherein. These terms are to be understood with reference to a directionof ingress into a vehicle, “forward”/“front”/“outboard” meaninggenerally toward the exterior of the vehicle, and“rearward”/“rear”/“inboard” meaning generally toward the interior of thevehicle. The depicted retractable vehicle step system 400 generallycomprises a powered step mechanism 420 and an idler step mechanism 440,both of which are connected to a stepping deck 460. Under powerdelivered by a drive system 480 drivingly connected to the powered stepmechanism 420, the powered and idler mechanisms 420, 440 move thestepping deck 460 between a retracted position (e.g., similar to theretracted position shown in FIG. 1A) and the deployed position depictedin FIG. 4. The deployed position is located downward and outboard of theretracted position.

In other embodiments, two powered step mechanisms 420 may be employed inplace of the combination of powered and idler mechanisms 420, 440depicted in FIG. 4, or only a single powered step mechanism 420 (and noidler mechanism 440 at all) may be employed to support and move thestepping deck 460. In still other embodiments, two or more idlermechanisms 440 may be employed in combination with one or more poweredmechanisms 420 to support and move the stepping deck 460.

Each of the powered step mechanism 420 and idler step mechanism 440comprises a four-bar linkage. Thus, the powered step mechanism 420includes a first arm 422 and a second arm 424, each of which ispivotably connected to a generally rigid frame 426. The frame 426 isconfigured to be secured to a vehicle (not shown), particularly theunderside thereof, via a mounting flange 428. The first and second arms422, 424 are therefore pivotable with respect to frame 426 aboutgenerally parallel first and second axes A-A, B-B, respectively. Whenthe retractable vehicle step system 400 is mounted on a vehicle, each ofthe first and second axes A-A, B-B is oriented generally parallel to theground. A support bracket 430 is rigidly connected to the stepping deck460, and is connected to the first and second arms 422, 424 so as to berotatable about third and fourth axes C-C, D-D, respectively. Thus, uponrotation of the first and second arms 422, 424 about the first andsecond axes A-A, B-B, the stepping deck 460 moves between the retractedposition and the deployed position.

Similarly, the idler step mechanism 440 includes a first arm 442 and asecond arm 444, each of which is pivotably connected to a generallyrigid frame 446. The frame 446 is configured to be secured to thevehicle alongside the powered frame 446 via a mounting flange 448. Thefirst and second arms 442, 444 are therefore pivotable with respect tothe frame 446 about the first and second axes A-A, B-B, respectively. Asupport bracket 450 is rigidly connected to the stepping deck 460, andis connected to the first and second arms 442, 444 so as to be rotatableabout the third and fourth axes C-C, D-D, respectively. Thus, uponrotation of the first and second arms 422, 424, 442, 444 about the firstand second axes A-A, B-B, the stepping deck 460 moves between theretracted position and the deployed position.

Either of the powered step mechanism 420 or the idler step mechanism 440may comprise any suitable retractable vehicle step mechanism, of whichthere are many presently known in the relevant arts. Of course, anysuitable later-developed mechanism may also be employed as either of thepowered and idler mechanisms 420, 440. In some embodiments, either ofthe powered and idler mechanisms 420, 440 may comprise any of theretractable-step mechanisms disclosed in U.S. Pat. No. 6,641,158, titledRetractable Vehicle Step, issued Nov. 4, 2003; or U.S. Pat. No.6,834,875 titled Retractable Vehicle Step, issued Dec. 28, 2004. Theentire contents of each of the above-mentioned patents are herebyincorporated by reference herein and made a part of this specification.

Exemplary Step System Installation

FIG. 5 is a flowchart depicting an exemplary method of installing anautomated vehicle step system. The method may be used to install anautomated step system to a host vehicle after market by the owner of thevehicle, for example, or by any other appropriate individual. Theinstalled step system can be any of the step systems described herein.

At step 502, the method includes installing the linkage and steppingdeck of the step system. The linkage and stepping deck may be similar tothe embodiments of FIGS. 1A-1B, 3, and 4, for example. For instance,referring to the step assist 400 of FIG. 4, the combination of the firstarm 422, second arm 424, support frame 426, and mounting flange 428 maycorrespond to the linkage, while the stepping deck 460 and supportingbrackets 430, 450 correspond to the stepping deck.

While the particular steps involved in installing the linkage andstepping deck can vary depending on the particular mechanical design, inone embodiment the operator attaches the linkage to the underside of thevehicle and attaches the stepping deck to the other side of the linkage.Where there are two sets of linkages such as is depicted in FIGS. 1A-1Band FIG. 4, step 502 also involves attaching the second linkage to thevehicle and to the stepping deck, which can be achieved in a mannersimilar to that used to attach the first linkage.

Installing the linkage in some embodiments involves removal of one ormore body mount bolts on the underside of the vehicle and fastening thelinkage to the vehicle using the body mount bolts or other appropriatefastening means. Installing the stepping deck can involve fastening thestepping deck to the linkage(s) using one or more fastening bolts orother fastening means. In some cases, the stepping deck is permanentlyattached to the linkages, and separate installation of the stepping deckis not necessary.

At step 504, the method includes installing the drive unit of the stepsystem. In some embodiments, this involves engaging a coupling of themotor of the drive unit with a corresponding coupling provided on thelinkage. For instance, a gear provided on the motor coupling can bemeshed with a corresponding gear on the linkage. Step 504 can alsoinclude fastening the motor to the linkage (e.g., using one or morefastening bolts), or directly to the vehicle depending on the design.

Step 506 involves installing the controller, which can be any of thecontrollers described herein. In some embodiments, the controllerhousing is positioned under the hood of the vehicle somewhere within theengine compartment. For instance, the controller housing in anembodiment is fastened to a support arm within the engine compartment.

At step 508, the method includes installing the vehicle interface. Thevehicle interface can be any of those described herein, including any ofthe vehicle interfaces 220 described with respect to FIGS. 2A-2F, or thevehicle interface 304 of FIG. 3. In some embodiments, step 508 includesattaching a connector of the vehicle interface to an existing port ofthe vehicle.

For instance, referring to FIG. 2A, step 508 can include coupling theport 224 of the vehicle interface 220 with the corresponding connectorof the OBD or other type of existing vehicle port 240, e.g., via afriction fit or interference fit. Referring to FIG. 2B, step 508 caninclude attaching the port 227 of the connector apparatus 226 to theexisting vehicle port 240, and attaching the port 224 of the connectormodule 222 to the first replica port 228.

As discussed above, in some embodiments, a replica port of the vehicleinterface, such as the second replica port 229 of the embodiment shownin FIG. 2B, can be physically positioned in place of the existingvehicle port 240 to provide normal access to the functionality of theexisting vehicle port 240. For instance, still referring to FIG. 2B, theexisting vehicle port 240 and its associated housing can be physicallydetached from its normal location under the dashboard, and repositionedat another location with respect to the vehicle. And the second replicaport 229 can be secured at the original location of the existing vehicleport 240, e.g., under the dashboard, using any suitable fastening meanssuch as adhesives, ties, or the like. Meanwhile, the other portions ofthe vehicle interface 220 including the port 227, the first replica port228, the connector module 222, and associated cabling can be positionedelsewhere. In one illustrative embodiment, step 508 of the installationmethod includes fastening these portions to the underside of thedashboard, such that these components are not visible from thepassenger's normal line of sight, for example. By positioning the secondreplica port 229 in place of the existing vehicle port 240, theinstallation is substantially transparent to technicians or otherindividuals desiring to access the functionality of the existing vehicleport 240. For instance, where the vehicle port 240 is an OBD port, atechnician may plug an OBD scanner into the second replica vehicle port229 to perform diagnostics without even knowing that he is connecting toa replica port rather than the original vehicle port 240.

A similar approach can be used with respect to the embodiment of thevehicle interface 220 shown in FIG. 2D. For instance, the connectormodule 222 of the vehicle interface 240 can be fastened or otherwisepositioned in place of the existing vehicle port 240, and the replicaport 229 can provide users with ready access to the functionality of theexisting vehicle port 240. Depending on the embodiment, the replica port229 may not be positioned at exactly the same position as the existingvehicle port 240. For instance, referring to FIG. 2B again, the existingvehicle port 240 (connected to the port 227 of the vehicle interface240) may be repositioned, e.g., out of sight, and the second replicaport 229 may be positioned at any appropriate location, such as someposition on the dashboard or within the footwell such that a user willbe able to readily recognize that the replica port 229 can be utilizedto access the functionality of the existing vehicle port 240.

Step 508 can in some embodiments include interposing the vehicleinterface 220 between an existing electrical junction or other existingconnection of the vehicle. For instance, referring to FIGS. 2E-2F, step508 can involve detaching the connector 242 from the electronic controlunit 250, attaching the port 224 of the connector module 222 to the nowunoccupied port 244 of the electronic control unit 250, and attachingthe replica port 229 of the connector module 222 to the connector 242 ofthe cabling 244 that was removed from the electronic control unit 250.In this manner, the vehicle interface 240 can be readily installed usingexisting vehicle connections, without altering normal vehicle operation.

At step 510, the method includes connecting and powering the componentsof the step system. For instance, referring to FIG. 2A for the purposesof illustration, the controller 210 in one embodiment is installed inproximity to the vehicle battery (step 506) and the wiring 216 is routedfrom the controller to the drive unit of the step system. For instance,the wiring 216 may be routed through the engine compartment (e.g., atleast partly alongside an existing wiring harness) and down through theengine compartment and into the front wheel well on the step-side of thevehicle. The wiring 216 is further routed to the underside of thevehicle and connected to the drive unit. Where more than one step ispresent, there may be multiple corresponding sets of wiring 216 that arerouted in a similar fashion to the respective drive units.

The wiring 218 may be routed from the connector 222 of the vehicleinterface 240 to the controller 210. For instance, where the connector222 is attached to a vehicle port 240 that is positioned in the mannershown in FIG. 2A, the wiring 218 may be routed from the vehicle port240, into the engine compartment, and then routed within the enginecompartment (e.g., at least partly alongside an existing vehicle wiringharness) to the controller 210 and connected to the port 214 of thecontroller 210.

The wiring 217 may be routed from the controller 210 to the vehiclebattery to provide power to the components of the installed step system.While shown as a sequence of separate steps for illustrative purposes,portions of activities described with respect to the individual stepsmay be performed together, and the steps can be performed in a differentorder. For instance, although step 510 is shown separately, differentportions of the step system may be connected together and/or powered atdifferent points in time during the install.

Exemplary Step System Operation

FIG. 6 is a flowchart depicting an exemplary method of operating a stepsystem. The step system can be any of the step systems described herein,for example. The control algorithm may be implemented by software orfirmware executing in one or more hardware processors of the vehicleinterface of the step system, the controller of the step system, such asthe vehicle interfaces 220 or controllers 210 of FIGS. 2A, 2B, and 2D,or the vehicle interface 304 or controller 306 of FIG. 3. For instance,the vehicle interface may provide outputs to the controller that thecontroller uses to instruct the drive unit, as discussed previously. Forthe purposes of illustration, certain aspects of the method aredescribed with respect to a running board style step assist such as theones shown in FIGS. 1A-1B and FIG. 4, which at least partially spans thelength of, and is used to assist user entry/exit with respect to, atleast front and rear doors. It will be understood, however, that themethod can apply to various other step assist configurations.

At decision block 602, the stepping deck is in a retracted position, andthe control algorithm specifies that the stepping deck will remain sountil a door on the running board-side of the car is opened. When thevehicle interface and/or controller determines that any door on therunning board-side of the car has been opened, the controller causes therunning board to deploy at step 604.

In another embodiment, there is only one step provided, e.g., under oneof the front door or the rear door, and in such a case the stepping deckwould deploy only if that particular door was opened. In yet anotherconfiguration, separate steps are provided for independent use with eachof the front and rear doors, and each step similarly deploys only if thedoor associated with that particular step is opened.

Returning to the two-door running board example, after detecting theopening of any door on the running board-side of the vehicle, the methodenters decision block 606. The control algorithm specifies that therunning board will remain deployed unless and until all of the doors onthe running-board. Once all of the doors are closed, the method leavesdecision block 606, and the step system retracts the stepping deck atstep 608. In some cases, the controller implements a delay beforeretracting the stepping deck at step 608 (e.g., of 1, 2, 3, 4, 5, ormore seconds).

Where only one step is provided for use with one door, or where separatestepping decks are provided for use with each of the front and reardoor, the stepping deck would retract at step 608 in response to closureof just that particular door, even if the other door remains opened.

After retraction of the stepping deck at step 608, the method returns todecision block 602 and the vehicle interface and/or controller againlistens for relevant door openings.

While the method has been described with respect to a step assist(s)installed on one side of the vehicle, one or more step assists can alsobe implemented on the opposing side of the vehicle, as discussedpreviously. In such a case, the step assist(s) on the opposing side canoperate in a similar manner and in response to the door(s) on theopposing side opening and closing. In an alternative embodiment, a stepassist installed on the passenger side deploys/retracts in response toone or more driver side doors opening/closing, or vice versa.

Operation of the stepping assist with respect to the method of FIG. 6has thus far been described for the purposes of illustration primarilywith respect to door opening and closing events. Such events can bedetected in any of the manners described herein. It will further beunderstood that a wide variety of inputs can be used instead of or inaddition to door opening and closing events, and that a variety ofdecisioning schemes can be used to control movement of the steppingdeck. The table below provides a simplified description of just a fewsuch examples.

Exemplary Exemplary Intermediary Originating Vehicle Vehicle Type ofStep Movement Component(s) Component(s) Information Decision Doorsubsystem(s) BCM, DCU, Door opened/ door open/ajar = (e.g., car door OBDport closed information deploy; module) (e.g., door ajar) door closed =retract Door subsystem(s) BCM, DCU, Door locked/ door unlocked = (e.g.,car door OBD port unlocked deploy; allow module) information deploymentdoor locked = retract; do not allow deployment Transmission system, TCU,Engine Vehicle speed speed > threshold Engine Computer, Control Unit,(e.g., >5 mph) = Speedometer Speed Control retract; do not allow Unitdeployment (even if door is open/ajar); speed < threshold (e.g., <5 mph)= allow deployment Vehicle Ignition Engine Control Vehicle engine on/vehicle off = allow system Unit, OBD port vehicle engine off deploymentvehicle on = retract; do not allow deployment Key FOB actuation BCM, DCUDoor door unlocked = sensor locked/unlocked deploy; using FOB doorlocked = retract Key FOB proximity BCM, DCU Driver approaching drivercrosses into sensor vehicle threshold proximity = deploy; driver crossesout of threshold proximity = retract Transmission system TCU, OBD portTransmission in park = deploy; status allow deployment in gear =retract; do not allow deployment

The above chart shows a simplified depiction of the step movementdecisioning process. It will be appreciated that a variety ofcombinations of the above or other inputs and decisioning schemes can beused to determine when to move the step. For example, while notspecifically illustrated in the flowchart, depending on the embodiment,input from an override switch can be used in combination with dooropening and closing information by the decisioning algorithm. Forinstance, it will be appreciated that the override would supercede thealgorithm set forth in the flowchart of FIG. 6. Another illustrativeexample which involves the use of a combination of vehicle speedinformation and door opening and closing information will now bedescribed.

As indicated in the above chart, vehicle speed can be used in some casesto control movement of the step. Vehicle speed information can originatefrom any appropriate vehicle electronics, such as a speedometer, enginecomputer, a wheel speed sensor or other speed sensor, a transmissionsystem component, or the like. Referring to FIG. 3, speed informationcan be forwarded directly to an OBD or other vehicle port 318. Or speedinformation can be sent to a vehicle computing system 316 (e.g., atransmission control unit (TCU), speed control unit (SCU), or enginecontrol unit (ECU)). The vehicle computing system 316 in such cases canprovide access to the speed information (e.g., after processing) via oneof the ports 334, 336 of the computing system 316, or can insteadprocess the speed information and forward the processed information toan OBD or other stand-alone port 318.

However obtained, the vehicle interface and/or step system controllercan utilize the vehicle speed information in concert with door openingand closing information, as desired. As one example, when the vehicle iseither not moving, or is moving, but below a threshold speed, the stepsystem retracts and deploys the step in response to door openings andclosings as indicated with respect to the flow chart above. However,when a step is deployed at the time the vehicle speed exceeds thethreshold speed, the algorithm specifies that the step will retract evenif a door is open (e.g., ajar). This can be useful where a door isslightly ajar or otherwise not completely closed, but the drivercontinues to drive the vehicle because it escapes her notice. Thealgorithm can additionally specify that while vehicle speed is above thethreshold, the step will not deploy, even in response to door openings.The threshold speed can vary, but can preferably be a relatively lowvalue in some cases, and in one embodiment is a value less than 5 mph.According to other embodiments, the threshold is a value less than 1, 2,10, 15, 20, 25, 30, or 40 mph, or falls within a range of between about1 mph and about 30 mph, between about 2 mph and about 20 mph, betweenabout 3 mph and about 15 mph, or within some other range. In yet othercases, the threshold value is about 3, 4, 5, 6, 7, 8, 9, 10, 15, or 20mph.

In another illustrative example, vehicle engine on/off information canbe used in combination with door opening and closing information. Forexample, step deployment may be disabled if the vehicle is running, evenif the corresponding door is opened.

Terminology/Additional Embodiments

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orstates. Thus, such conditional language is not generally intended toimply that features, elements and/or states are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or states are included or are to beperformed in any particular embodiment.

Depending on the embodiment, certain acts, events, or functions of anyof the methods described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not alldescribed acts or events are necessary for the practice of the method).Moreover, in certain embodiments, acts or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores, rather thansequentially.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein can be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. The described functionalitycan be implemented in varying ways for each particular application, butsuch implementation decisions should not be interpreted as causing adeparture from the scope of the disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein can be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor can be a microprocessor, but in thealternative, the processor can be any conventional processor,controller, microcontroller, or state machine. A processor can also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The blocks of the methods and algorithms described in connection withthe embodiments disclosed herein can be embodied directly in hardware,in a software module executed by a processor, or in a combination of thetwo. A software module can reside in RAM memory, flash memory, ROMmemory, EPROM memory, EEPROM memory, registers, a hard disk, a removabledisk, a CD-ROM, or any other form of computer-readable storage mediumknown in the art. An exemplary storage medium is coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium can beintegral to the processor. The processor and the storage medium canreside in an ASIC. The ASIC can reside in a user terminal. In thealternative, the processor and the storage medium can reside as discretecomponents in a user terminal.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, certain embodiments of the disclosures described herein canbe embodied within a form that does not provide all of the features andbenefits set forth herein, as some features can be used or practicedseparately from others. The scope of certain disclosures disclosedherein is indicated by the appended claims rather than by the foregoingdescription. All changes which come within the meaning and range ofequivalency of the claims are to be embraced within their scope.

What is claimed is:
 1. An accessory system configured for use with avehicle, comprising: a vehicle interface comprising: a first connectorconfigured to removably attach to an already existing electronics portof a vehicle and to electronically receive data via the existingelectronics port, the data generated by existing electronics of thevehicle; and a second connector comprising a replica of the existingelectronics port, the vehicle interface configured to output at thesecond connector the data received by the first connector; and anaccessory configured to mount to the vehicle and responsive to the datareceived by the vehicle interface from the already existing electronicsport to perform one or more operations, wherein the received datacomprises one or more of first information relating to the status of adoor of the vehicle and second information relating to an electronic keyassociated with the vehicle.
 2. The system of claim 1, wherein thevehicle interface includes a cable spanning between the first connectorand the second connector.
 3. The system of claim 2, wherein the vehicleinterface further comprises a third connector, and wherein electronicsof the accessory are coupled to the vehicle interface via connection tothe third connector.
 4. The system of claim 1, wherein the firstconnector and the second connector are provided on a common housing. 5.The system of claim 1, wherein the first information comprises dooropened/closed status information.
 6. The system of claim 1, wherein thesecond information comprises information relating to actuation of abutton provided on the electronic key.
 7. The system of claim 1, whereinthe second information comprises information relating to detectedphysical proximity of the electronic key in relation to the vehicle. 8.A system configured for use with a vehicle, comprising: a vehicleinterface comprising: a first connector configured to attach to analready existing electronics port of a vehicle and to electronicallyreceive data via the existing electronics port, the data generated byexisting electronics of the vehicle; a second connector; andpass-through componentry coupled to the first connector and the secondconnector and configured to transmit the data received at the firstconnector to the second connector; and an accessory configured to mountto the vehicle and responsive to the data received by the vehicleinterface from the already existing electronics port to perform one ormore operations, wherein the received data comprises door statusinformation.
 9. The system of claim 8, wherein the pass-throughcomponentry comprises a cable spanning between the first connector andthe second connector.
 10. The system of claim 9, wherein the vehicleinterface further comprises a third connector, and wherein electronicsof the accessory are coupled to the vehicle interface via connection tothe third connector.
 11. The system of claim 8, wherein the firstconnector and the second connector are provided on a common housing. 12.The system of claim 8, wherein the door status information comprisesdoor opened/closed status information.
 13. A system configured for usewith a vehicle, comprising: a vehicle interface comprising: a firstconnector configured to attach to an already existing electronics portof a vehicle and to electronically receive data via the existingelectronics port, the data generated by existing electronics of thevehicle; a second connector; and pass-through componentry coupled to thefirst connector and the second connector and configured to transmit thedata received at the first connector to the second connector; and anaccessory configured to mount to the vehicle and responsive to the datareceived by the vehicle interface from the already existing electronicsport to perform one or more operations, wherein the received datacomprises information relating to an electronic fob associated with thevehicle.
 14. The system of claim 13, wherein the pass-throughcomponentry comprises a cable spanning between the first connector andthe second connector.
 15. The system of claim 14, wherein the vehicleinterface further comprises a third connector, and wherein electronicsof the accessory are coupled to the vehicle interface via connection tothe third connector.
 16. The system of claim 13, wherein the firstconnector and the second connector are provided on a common housing. 17.The system of claim 13, wherein the received data comprises informationrelating to actuation of a button provided on the electronic fob. 18.The system of claim 13, wherein the received data comprises informationrelating to detected physical proximity of the electronic fob inrelation to the vehicle.
 19. The system of claim 13, wherein theelectronic fob comprises a vehicle key.